src/drivers/magnetometer/bosch/bmm350/BMM350.cpp: Publish initial 0 d… #815
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joukkone
approved these changes
Nov 18, 2024
…hen creating magnetometer driver instance This ensures that magnetometers instance numbers are allocated in the driver start order. It is problematic if the magnetometers get different IDs on different HW even if the start order of the drivers in the init scripts is the same. Signed-off-by: Jukka Laitinen <[email protected]>
jlaitine
force-pushed
the
fix_mag_start_order
branch
from
05459a2 to
f2e5c23
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…ata to register mags in module start order
Magnetometer numbers are allocated in the order when the first data gets published to sesors module.
It is problematic if the magnetometers get different IDs on different HW even if the start order of the drivers in the init scripts is the same.
Therefor, publish some dummy data right after successful probe of the driver